Enabling multi-network path aware applications

ABSTRACT

An apparatus is provided which comprises at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform providing information concerning multiple networks to at least one application, receiving instructions from the application, and managing traffic relating to the at least one application on the multiple networks based on the instructions received from the application.

FIELD OF THE INVENTION

The present invention relates to an apparatus, a method and a computerprogram product by which it is possible to enable multi-network pathaware applications.

RELATED BACKGROUND ART

The following meanings for the abbreviations used in this specificationapply:

-   -   3GPP 3rd Generation Partnership Project    -   API Application Programming interface.    -   C-MADP Client Multi-Access Data Proxy    -   CCM Client Connection Manager    -   DSL Digital Subscriber Line    -   HTTPS Secure Hypertext Transfer Protocol    -   IETF Internet Engineering Task Force    -   LTE Long Term Evolution (4G)    -   MAMS Multiple Access Management Services    -   MEC Multi-access Edge Computing    -   N-MADP Network Multi-Access Data Proxy    -   NCM Network Connection Manager    -   UE user equipment    -   URLLC ultra-reliable and low latency communications

Embodiments of the present invention, although not limited to this,relate to multi-network path and multi-access technologies, wherein itis possible for a device to be connected to multiple access technologies(like LTE, Wi-Fi 5G and more) at the same time and utilize multiplepaths for data transfer to the application (which itself is notgenerally multi-access aware) using a Multi-Path Network Manager. Insuch scenarios, the multi-path network manager provides both the controland user plane functionality of managing and aggregating the variousflows and controlling the distribution of traffic across technologiesbased on parameters such as conditions of each access technology, devicecapabilities etc.

For example, document “Multiple Access Management Services” (MAMS) by S.Kanugovi et al (INTAREA IETF draft-kanugovi-intarea-mams-protocol-05),Sep. 27, 2017, describes such multi-network path and multi-accesstechnologies.

SUMMARY OF THE INVENTION

Embodiments of the present invention aim to improve flexibility andperformance of applications in such multi-network path and multi-accesstechnologies.

According to a first aspect of the present invention, an apparatus isprovided which comprises at least one processor, at least one memoryincluding computer program code, and the at least one processor, withthe at least one memory and the computer program code, being arranged tocause the apparatus to at least perform providing information concerningmultiple networks to at least one application, receiving instructionsfrom the application, and managing traffic relating to the at least oneapplication on the multiple networks based on the instructions receivedfrom the application.

According to a second aspect of the present invention, a method isprovided which comprises:

-   -   providing information concerning multiple networks to at least        one application,    -   receiving instructions from the application, and    -   managing traffic relating to the at least one application on the        multiple networks based on the instructions received from the        application.

The first aspect and the second aspect may be modified as follows:

For example, the information concerning multiple networks may besubscriber based.

Moreover, upon managing traffic related to the at least one application,the traffic relating to the at least one application may be distributedon the multiple networks based on the instructions received from theapplication.

The traffic relating to the at least one application may be distributedon the multiple access networks separately for uplink and downlinkdirections.

The at least one application may be informed how the traffic isdistributed on the multiple networks.

Information may be acquired from a network provider management functionelement, and the application may be provided with the information fromthe network provider management function element and/or managing thetraffic relating to the at least one application based on theinformation from the network provider management function element.

A dedicated interface (e.g., a RESTful interface) may be providedbetween the apparatus and the at least one application for exchanginginformation with the at least one application.

The at least one application may be run by an application server, andexchanging information with the at least one application may beperformed by exchanging information with the application server.

The information concerning multiple networks may comprise conditionsincluding availability of networks, network load and/or costs.

According to a third aspect of the present invention, an apparatus isprovided which comprises at least one processor, at least one memoryincluding computer program code, and the at least one processor, withthe at least one memory and the computer program code, being arranged tocause the apparatus to at least perform running an application,receiving information concerning multiple networks from a networkcontrol element, creating instructions for managing the multiple networkrelating to the application based on the received information, andsending the instructions to the network control element.

According to a fourth aspect of the present invention, a method isprovided which comprises:

-   -   running an application,    -   receiving information concerning multiple networks from a        network control element,    -   creating instructions for managing the multiple network relating        to the application based on the received information, and    -   sending the instructions to the network control element.

The third aspect and the fourth aspect may be modified as follows:

For example, the apparatus or the apparatus carrying out the method mayregister with the network element for obtaining the informationconcerning multiple networks, and/or subscribe to related messages withthe network control element.

The information concerning multiple networks may be subscriber based.

Information may be received from the network control element how thetraffic is distributed on the multiple networks.

Information may be exchanged between the apparatus or the apparatuscarrying out the method with the network control element via a dedicatedinterface.

According to a fifth aspect of the present invention a computer programproduct is provided which comprises code means for performing a methodaccording to the second aspect and/or fourth aspect and/or theirmodifications when run on a processing means or module. The computerprogram product may be embodied on a computer-readable medium, and/orthe computer program product may be directly loadable into the internalmemory of the computer and/or transmittable via a network by means of atleast one of upload, download and push procedures.

According to a sixth aspect of the present invention an apparatus isprovided which comprises

-   -   means for providing information concerning multiple networks to        at least one application,    -   means for receiving instructions from the application, and    -   means for managing traffic relating to the at least one        application on the multiple networks based on the instructions        received from the application.

According to a seventh aspect of the present invention an apparatus isprovided which comprises

-   -   means for running an application,    -   means for receiving information concerning multiple networks        from a network control element,    -   means for creating instructions for managing the multiple        network relating to the application based on the received        information, and    -   means for sending the instructions to the network control        element.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects, features, details and advantages will becomemore fully apparent from the following detailed description ofembodiments of the present invention which is to be taken in conjunctionwith the appended drawings, in which:

FIG. 1A illustrates a multi-network path manager according to anembodiment of the present invention,

FIG. 1B illustrates a method of a multi-network path manager accordingto an embodiment of the present invention,

FIG. 2A illustrates an application server according to an embodiment ofthe present invention,

FIG. 2B illustrates a method of an application server according to anembodiment of the present invention,

FIG. 3 illustrates an architectural view in which embodiments of thepresent invention can be applied,

FIG. 4 shows basic procedures according to an embodiment of the presentinvention, and

FIG. 5 shows an implementation example according to an embodiment of thepresent invention.

DETAILED DESCRIPTION OF EMBODIMENTS

In the following, description will be made to embodiments of the presentinvention. It is to be understood, however, that the description isgiven by way of example only, and that the described embodiments are byno means to be understood as limiting the present invention thereto.

Before describing embodiments, however, the problem underlying thepresent application is described in some more detail.

That is, in multi-network path and multi-access technologies accordingto the prior art, applications have no means to differentially chargesuch distribution of traffic across various access technologies based ontype of subscription or application host needs.

In more detail, in most cases application servers are not aware ofmultiple networks being used by end device with the help of technologieslike MPTCP-proxies or using methods as defined in “Multiple AccessManagement Services” (MAMS) by S. Kanugovi et al (INTAREA IETFdraft-kanugovi-intarea-mams-protocol-05), Sep. 27, 2017. Thedistribution and usage of multi-access is decided between the end deviceand the multi-path network manager. This system provides for controlplane interaction between the device (using an entity called ClientControl Manager—CCM) and the multi-network path manger (using an entitycalled Network Control Manager—NCM). It also provides for data planeentities in the device and the multi network path manager called ClientMulti-Access Data Proxy (C-MADP) and Network Multi-Access Data Proxy(N-MADP) respectively.

The current state of the art considers the aspects related to networkand client discovering about presence of multiple interfaces andnetworks and making use of these based on network and client parameters.These prior art do not involve application servers making any decisionabout usage of multiple networks based on subscriber's parameters. Theusage of multiple networks is done based on the device's capability andmeasurements from the various access technologies.

Embodiments of the present invention aim to improve flexibility andperformance of applications in such multi-network path and multi-accesstechnologies by providing measures which enable applications to be awareof multiple networks.

In the following, a general overview of an embodiment of the presentinvention is described by referring to FIGS. 1A, 1B, 2A and 2B.

In particular, FIG. 1A shows a multi-network path manager 1 as anexample for a first apparatus or a network control element according tothe present embodiment. The multi-network path manager 1 comprises atleast one processor 11 and at least one memory 12 including computerprogram code. The at least one processor 11, with the at least onememory 12 and the computer program code, is arranged to cause theapparatus to at least perform providing information concerning multiplenetworks to at least one application, receiving instructions from theapplication, and managing traffic relating to the at least oneapplication on the multiple networks based on the instructions receivedfrom the application.

In other words, by referring to the flowchart shown in FIG. 1B, in stepS11 information concerning multiple networks is provided to at least oneapplication (which is run in an application server shown in FIG. 2A, forexample). In step S12, instructions from the application are received,which, for example, may indicate how traffic relating to the at leastone application should be distributed on the multiple networks, and instep S13, the traffic is managed based on the instructions received fromthe at least one application.

FIG. 2A shows an application server 2 as an example for a secondapparatus according to the present embodiment. The application server 2comprises at least one processor 21 and at least one memory 22 includingcomputer program code. The at least one processor 21, with the at leastone memory 22 and the computer program code, is arranged to cause theapparatus to at least perform running an application, receivinginformation concerning multiple networks from a network control element,creating instructions for managing the multiple network relating to theapplication based on the received information, and sending theinstructions to the network control element.

That is, by referring to the flowchart shown in FIG. 2B, the applicationserver 2, which runs at least one application, receives in step S21information concerning multiple networks from the network controlelement, which may be the multi-network path manager 1 shown in FIG. 1A,for example. In step S22, instructions for managing the multiplenetworks are created based on the received information concerning themultiple networks. In step S23, the instructions are sent to the networkcontrol element.

Thus, according to embodiments of the present invention, the at leastone application is aware of the multiple networks, and cancorrespondingly instruct the network control element how the trafficshould be managed.

The information may be subscriber-based, that is, the informationconcerning the multiple networks may be different for each subscriber,depending on usage limits, policies etc. set for each subscriber.

Managing of the traffic related to the at least one application maycomprise distributing the traffic on the multiple networks. For example,a certain percentage of the traffic may be transmitted via a firstnetwork, and the remaining percentage of the traffic may be transmittedvia a second network.

The multi-network path manager 1 may further comprise input/output (I/O)units or functions (interfaces) 13 connected to the processor 11, inorder to provide connections to other elements such as a user device andto the application server 2, for example. In particular, the I/O unitsor functions 13 may comprise different receiver/transmitter unitsnecessary for the multiple networks.

Moreover, the application server 2 may further comprise input/output(I/O) units or functions (interfaces) 23 connected to the processor 21,in order to provide connections to other elements in a network, inparticular to the multi-network path manager 1.

In the following, some more details of embodiments of the presentinvention are described.

FIG. 3 illustrates a high level architectural view of multiple-networkspath based access, to which embodiments of the present invention can beapplied.

In particular, a device 31 is connected to a multi-network path manager34 (which may be the multi-network path manager 1 shown in FIG. 1A) viatwo different access network, namely a first access network 32 and asecond access network 33. The multi-network path manager is connected tonetwork provider functions 35 and with an application server 36 (whichmay be the application server 2 shown in FIG. 2A).

The device 31, which is a client, and in this particular case amulticonnectivity client, comprises a client connection manager (CCM)311, a first access means 312 for the first access network 32, a secondaccess means 313 for the second access network 33, a client multi accessdata proxy (C-MADP) 314 and an application client (app client) 315 asfunctional entities.

The multi-network path manager 34 comprises a network connection manager(NCM) 341 and a network multi access data proxy (N-MADP) 342 asfunctional entities.

The CCM 311 is a functional entity in the client that exchanges MAMSSignaling with the network connection manager (NCM) 341 in themulti-network path manager 34 and configures the multiple network pathsfor transport of user data.

The C-MADP 314 is a functional entity in the client that handles theuser data traffic forwarding across multiple network paths. C-MADP isresponsible for MAMS related user-plane functionalities in the client.

The NCM 341 is a functional entity in the multi-network path manager 34that oversees distribution of data packets over the multiple availableaccess and core network paths.

The N-MADP 342 is a functional entity in the multi-network path manager34 handles the user data traffic forwarding across multiple networkpaths. The N-MADP is responsible for MAMS related user-planefunctionalities in the network.

As derivable from FIG. 3 , a control flow between CCM 311 and the NCM341 extends over both access networks 32 and 33 via both access means312 and 313. Data flows extends between the application client 315 andthe C-MAPD 314, and between the application server 36 and the N-MAPD342. This data flow is transmitted between the C-MADP 314 and the N-MAPD342 over both access networks 32 and 33 via both access means 312 and313.

Within such a configuration, embodiments of the present inventionprovide for following:

-   -   According to embodiments of the present application,        application(s) connected to Multi-Path Network Manager is (are)        enabled to be aware of multi-networks and conditions (like        availability, network load, cost etc.) of each network.

In contrast thereto, current prior art methods do not provide thisinformation to application even though the information is available withthe network elements themselves.

-   -   According to embodiments of the present application, such an        application is allowed to instruct the multi-network path        manager to distribute the traffic to various network access        technologies separately for uplink and downlink direction based        on parameters known to application (e.g. subscribers profile,        subscription type, location etc.). It is noted that the NCM 341        (the NCM component) of the multi-network path manager 34        communicates the decision to the CCM 311 (the CCM component) in        the device 31 using MAMS.

In contrast thereto, current prior art performing trafficsteering/distribution do not consider preference from the applicationbeing served. They perform the action based on information availablefrom network only e.g. measurements from device, interface availability.

-   -   According to embodiments of the present application, in case of        application driven distribution of traffic across multi-network        paths the multi-network path manager provides report of such        distribution to the application for it to enable differential        (premium) rate of charging for such subscribers.

In contrast thereto, current prior art applications are not given anyreport of actual usage of traffic across multiple networks for any kindof differential charging by the application itself.

The above functionalities according to embodiments of the presentapplication are illustrated in FIG. 4 .

In E1, the multi-network path manager 34 acquires usage limits andpolicies for a subscriber, which is identified by a subscriber id. Thisis effected via a HTTPS server 343 in the multi-network path manager 34.

In E2, the multi-network path manager 34 informs multi-networkcapability for the subscriber.

In E3, the application (application server 36) sends a proposeddistribution for the subscriber to the multi-network path manager 34,for example by including a percentage of the distribution in UL and apercentage of distribution in DL. Communication between the applicationserver 36 can be performed via a HTTPS server 361 in the multi-networkpath manager 34 and the HTTPS server 343 in the multi-network pathmanager 34

In E4, the multi-network path manager 34 informs the multi-network usageof the subscriber.

A more detailed implementation is described in the following.

In this example, the multi-network path manager 34 implements a RESTfulinterface to exchange information with the hosted applications. Theseevents can be

-   -   a) device capability about multi-networks,    -   b) addition of new network,    -   c) mobility related events,    -   d) measurement of various networks accessed by device    -   e) removal of network etc.

Moreover, the multi-network path manager 34 implements an interface withthe Network Provider Management functions to exchange information onupdate of usage for charging, set overall usage limits, etc.

Additionally, there can be publication of following kind of informationwhich is not device specific:

-   -   a) Utilization of each network access    -   b) Load/Overload conditions (say at cells or access points)    -   c) Availability of a network path    -   d) Cost set by operator for each access technology (premium        access and non-premium access)

A multi-network aware application can subscribe to related messages withthe multi-network path manager 34. In this example implementationscenario both the multi-network path manager and the application server36 host a HTTP(S) server, as indicated by reference numerals 343 and361.

FIG. 5 represents a flow for a sample application according to anembodiment of the present invention.

In F1, the multi network path manager 34 gets information on overallaccess usage limits and policies from the network provider function 35(e.g. Charging).

In F2, the application registers itself and subscribes to messages ofits interest (such as admission of new subscriber in multi-network path,addition of a new network path, deletion of a network path etc.) withthe multi-network path manager 34 using HTTPS POST request.

As indicated by the dashed arrow in F2, the multi-network path manager34 registers the application's request and responds with OK.

In F3, on admitting a new subscriber with multi-network path capability,the multi-network path manager 34 informs the registered application(using HTTPS POST) with subscriber Id and details of the subscriber andthe type of a first network (e.g., access network #1).

In F4, on addition of a new network path (e.g., via access network #2)the multi-network path manager 34 informs the application (using HTTPSPOST) about this along with details of the new addition.

In F5, the application determines, based on its internal logic,subscriber's profile, subscription type, available capacity, etc. aproportionate distribution for uplink and downlink direction of trafficflow. The application can send a request of desired proportions to themulti-network path manager 34 using HTTPS POST. The application canchoose to vary this at any point of time depending on the actual usageor change subscriber's parameters/profile, quality indicator of eachnetwork, load of system etc. Moreover, as indicated by the dashed arrow,the multi-network path manager 34 sends a response to confirm that theinstruction is taken care of. Alternatively, the multi-network pathmanager 34 may also return an error to the application (the applicationserver) 36, in case the multi-network path manager 34 cannot for somereason follow the instructions.

In F6, the multi-network path manager 34 keeps sending network details(quality indication, utilization, cost, delay etc.), by using HTTPSPOST, of each the network that the subscriber is connected to at regularinterval.

In A, it is indicated that the application at any time can send a HTTPSGET request to the Multi-Network Path Manager to know the details of allsubscribers which are being served by the application along with detailsof the networks they are connected to and their details.

In B, it is indicated that the application can any time send a HTTPS GETrequest to Multi-Network Path Manager to acknowledge details about asubscriber. One typical usage of this information could be charge thesubscriber based on the actual usage of each of the network access typesbase on a differential cost and subscriber's profile/subscription.

Moreover, the multi-network path manager 34 provides usage informationto the network provider function 35.

With this implementation, it is possible for application to instructdistribution of traffic separately in uplink and downlink directionsacross various access technologies based on parameters like subscriberprofile, quality indicator of each network access, cost of accessingeach network as set by respective operator/owner of the network etc. Theapplication can get to know about the actual usage across variousnetworks and have an option of charging the subscriber differentiallybased on access technologies used.

The multi-access part of Multi-Network Path Manager can be implementedas defined in IETF MAMS specifications.

In the following, a real life example is described:

A premium subscriber (capable of using multiple networks) of a messengerservice (an application which is aware of multi-network capabilities andalready registered with multi-network path manager (corresponding tostep F2 in FIG. 5 )) joins using WiFi network, this information iscommunicated by multi-network path manager to the application(corresponding to step F3 in FIG. 5 ). After a time, subscriber joinsLTE network (corresponding to step F4 in FIG. 5 ). The messenger servicedetermines that this is a premium subscriber and that LTE is having abetter quality and asks the multi-network path manager 34 to shiftuplink from WiFi to LTE completely and downlink to use LTE 50% of time(corresponding to step F5 in FIG. 5 ). At the end of transaction themessenger service requests for a report from multi-network path manager(corresponding to step B in FIG. 5 ), and charge the user as persubscription.

For a non-premium user in similar case the messenger service can decideto continue with WiFi even when this subscriber joins LTE and LTE isproviding better service.

Hence, according to embodiments of the present invention, applicationscan be aware of multiple networks and can make use of the multiplenetworks. Thus, flexibility for the applications is improved.

The invention is not limited to the specific embodiments describedabove, and various modifications are possible.

For example, in the above embodiments, it was described that themultiple networks comprise different access networks technologies.However, the invention is not limited to this. That is, the differentnetworks may have the same technology. For example, when a WiFiconnection is used, the different network may use different frequencybands for the WiFi connection. Similar may apply to LTE and othernetwork technologies.

Moreover, in the above embodiments, HTTPS is used. However, HTTPS isonly an example, and any other secure means of communication can also beused between the entities.

Moreover, in the examples shown in FIGS. 3 to 5 only two access networksare shown. However, the number of the access network is not limited totwo and can be any number higher than 1.

For the purpose of the present invention as described herein above, itshould be noted that

-   -   method steps likely to be implemented as software code portions        and being run using a processor at a network element or terminal        (as examples of devices, apparatuses and/or modules thereof, or        as examples of entities including apparatuses and/or modules        therefore), are software code independent and can be specified        using any known or future developed programming language as long        as the functionality defined by the method steps is preserved;    -   generally, any method step is suitable to be implemented as        software or by hardware without changing the idea of the        invention in terms of the functionality implemented;    -   method steps and/or devices, units or means likely to be        implemented as hardware components at the above-defined        apparatuses, or any module(s) thereof, (e.g., devices carrying        out the functions of the apparatuses according to the        embodiments as described above, eNode-B etc. as described above)        are hardware independent and can be implemented using any known        or future developed hardware technology or any hybrids of these,        such as MOS (Metal Oxide Semiconductor), CMOS (Complementary        MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter        Coupled Logic), TTL (Transistor-Transistor Logic), etc., using        for example ASIC (Application Specific IC (Integrated Circuit))        components, FPGA (Field-programmable Gate Arrays) components,        CPLD (Complex Programmable Logic Device) components or DSP        (Digital Signal Processor) components;    -   devices, units or means (e.g. the above-defined apparatuses, or        any one of their respective means) can be implemented as        individual devices, units or means, but this does not exclude        that they are implemented in a distributed fashion throughout        the system, as long as the functionality of the device, unit or        means is preserved;    -   an apparatus may be represented by a semiconductor chip, a        chipset, or a (hardware) module comprising such chip or chipset;        this, however, does not exclude the possibility that a        functionality of an apparatus or module, instead of being        hardware implemented, be implemented as software in a (software)        module such as a computer program or a computer program product        comprising executable software code portions for execution/being        run on a processor;    -   a device may be regarded as an apparatus or as an assembly of        more than one apparatus, whether functionally in cooperation        with each other or functionally independently of each other but        in a same device housing, for example.

It is noted that the embodiments and examples described above areprovided for illustrative purposes only and are in no way intended thatthe present invention is restricted thereto. Rather, it is the intentionthat all variations and modifications be included which fall within thespirit and scope of the appended claims.

The invention claimed is:
 1. An apparatus, comprising: at least oneprocessor; and at least one memory including computer program code, theat least one processor, with the at least one memory and the computerprogram code, being configured to cause the apparatus to at leastperform providing information concerning multiple networks to at leastone application, receiving instructions from the application, andmanaging traffic relating to the at least one application on themultiple networks based on the instructions received from theapplication.
 2. The apparatus according to claim 1, wherein theinformation concerning multiple networks are subscriber based.
 3. Theapparatus according to claim 1, wherein the at least one processor, withthe at least one memory and the computer program code, is configured tocause the apparatus to further perform upon managing traffic related tothe at least one application, distributing the traffic relating to theat least one application on the multiple networks based on theinstructions received from the application.
 4. The apparatus accordingto claim 3, wherein the at least one processor, with the at least onememory and the computer program code, is configured to cause theapparatus to further perform distributing the traffic relating to the atleast one application on the multiple access networks separately foruplink and downlink directions.
 5. The apparatus according to claim 1,wherein the at least one processor, with the at least one memory and thecomputer program code, is configured to cause the apparatus to furtherperform acquiring information from a network provider managementfunction element, and providing the application with the informationfrom the network provider management function element or managing thetraffic relating to the at least one application based on theinformation from the network provider management function element. 6.The apparatus according to claim 1, wherein the at least one applicationis run by an application server, and the at least one processor, withthe at least one memory and the computer program code, is configured tocause the apparatus to further perform exchanging information with theat least one application by exchanging information with the applicationserver.
 7. An apparatus, comprising: at least one processor; and atleast one memory including computer program code, the at least oneprocessor, with the at least one memory and the computer program code,being configured to cause the apparatus to at least perform running anapplication, receiving information concerning multiple networks from anetwork control element, creating instructions for managing the multiplenetworks relating to the application based on the received information,sending the instructions to the network control element; and performregistering with the network control element for obtaining theinformation concerning multiple networks, or subscribing to relatedmessages with the network control element.
 8. The apparatus according toclaim 7, wherein the information concerning multiple networks aresubscriber based.
 9. A method, comprising: providing informationconcerning multiple networks to at least one application; receivinginstructions from the application; and managing traffic relating to theat least one application on the multiple networks based on theinstructions received from the application.
 10. The method according toclaim 9, wherein the information concerning multiple networks aresubscriber based.
 11. The method according to claim 9, furthercomprising: upon managing traffic related to the at least oneapplication, distributing the traffic relating to the at least oneapplication on the multiple networks based on the instructions receivedfrom the application.
 12. The method according to claim 11, furthercomprising: distributing the traffic relating to the at least oneapplication on the multiple access networks separately for uplink anddownlink directions.
 13. The method according to claim 11, furthercomprising: informing the at least one application how the traffic isdistributed on the multiple networks.
 14. The method according to claim9, further comprising: acquiring information from a network providermanagement function element; and providing the application with theinformation from the network provider management function element ormanaging the traffic relating to the at least one application based onthe information from the network provider management function element.